@erincandescent @jhaas @alexband I can’t prevent you from advertising prefixes to me.

I can filter / not accept the unwelcomed prefix(es) from you.

@erincandescent @jhaas @alexband my message is about preventing advertisement vs accepting said advertisement.

You can’t prevent someone from doing something. But you can not be part of their actions.

@alexband @jhaas that timing feels about like when I started paying attention to and hoping for RPKI. But not holding my breath.

@jhaas @alexband I absolutely agree that the information needs to be published for recipients to be able to make a decision / filter received prefixes.

My point was that simply publishing information doesn’t prevent anything.

@alexband I have yet to see how RPKI / ASPA / ROA can actually prevent route leaks.

I absolutely agree that they can help detect and mitigate route leaks AS LONG AS peers are using information published via RPKI / ROA.

Much like SPF can’t prevent spam. While SPF does make it easier to detect and filter spam.

Preventing is proactive and decidedly different than reactively detecting and mitigating (filtering).