nanog mailing list archives
Re: Prefix hijacking, how to prevent and fix currently
From: Brandon Butterworth <brandon () rd bbc co uk>
Date: Fri, 29 Aug 2014 10:28:48 +0100 (BST)
From: Saku Ytti <saku () ytti fi> I feel RPKI would be much more marketable if vendors would implement 'loose' mode. Loose mode would drop failing routes, iff there is covering (i.e. less specific is ok) route already in RIB.
+10
And it would completely remove false-positive blackholing.
This is why I don't want strict. That and true-positives, I don't think having a switch that allows courts/rir finger trouble etc to take out global routing is sensible. Too many others would start using it. However loose mode could be abused in the same way, they just invalidate your key and advertise a covering route to give themselves effective strict over you. Admittedly there is collateral damage to adjacent address space incurred in doing this but we know there are hijack techniques they could use to mitigate that brandon
Current thread:
- Re: Prefix hijacking, how to prevent and fix currently, (continued)
- Re: Prefix hijacking, how to prevent and fix currently George, Wes (Aug 29)
- Re: Prefix hijacking, how to prevent and fix currently Randy Bush (Aug 29)
- Re: Prefix hijacking, how to prevent and fix currently George, Wes (Aug 29)
- Re: Prefix hijacking, how to prevent and fix currently Randy Bush (Aug 29)
- Re: Prefix hijacking, how to prevent and fix currently George, Wes (Aug 29)
- Re: Prefix hijacking, how to prevent and fix currently Matthew Kaufman (Aug 29)
- Re: Prefix hijacking, how to prevent and fix currently Rob Seastrom (Aug 29)
- Re: Prefix hijacking, how to prevent and fix currently Jared Mauch (Aug 29)
- Re: Prefix hijacking, how to prevent and fix currently Matthew Kaufman (Aug 31)
- Re: Prefix hijacking, how to prevent and fix currently Nick Hilliard (Aug 31)
- Re: Prefix hijacking, how to prevent and fix currently Saku Ytti (Aug 31)
- Re: Prefix hijacking, how to prevent and fix currently Matthew Petach (Aug 31)
