[as112-ops] RPKI-signature for AS112-Prefixes
Warren Kumari
warren at kumari.net
Fri Jul 27 21:17:27 UTC 2018
On Fri, Jul 27, 2018 at 2:15 PM Carlos M. Martinez
<carlosm3011 at gmail.com> wrote:
>
> Indeed, that it’s also true. We have two cases already in our region
> (NAP.ec and CRIX).
>
A clarification -- the above said "strict filtering and only accept
prefixes which have a state "valid".". I had thought that NAP.ec and
CRIX dropped invalid, but accepted unknown / not found -- perhaps my
information is out of date; do these both now accept *only* 'valid'?
The presentation
(https://www.ripe.net/support/training/ripe-ncc-educa/presentations/use-cases-mauricio-oviedo.pdf)
from CRIX (April 2018) implied that unknowns were still accepted. I
was not able to find anything current on the NAP.ec page (most RPKI
related stuff is from ~2013, 2014. I was not able to parse the 2017
PDF)
W
> thanks!
>
> /Carlos
>
> On 27 Jul 2018, at 15:12, Jens Ott - Opteamax GmbH wrote:
>
> > One argument could also be, that some IXP-routeservers are already
> > strict filtering and only accept prefixes which have a state "valid".
> > Especially small ASNs not running their own AS112 node and not getting
> > direct peerings with someone running an AS112 node could see the
> > prefixes over the routeservers.
> _______________________________________________
> as112-ops mailing list
> as112-ops at lists.dns-oarc.net
> https://lists.dns-oarc.net/mailman/listinfo/as112-ops
--
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
---maf
More information about the as112-ops
mailing list