> 666.42.0.0/16 has a roa for as 777 > > you start receiving > > 666.42.0.0/24 and 666.42.1.0/24, both unsigned. Changing preference > isn't enough to stop routing, as it's a more specific route and > automatically wins if it gets into the table.
nope when there is no roa for the arriving prefix, a roa for the covering prefix is used. see draft-pmohapat-sidr-pfx-validate-07.txt. randy
