<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<span class="tlid-translation translation" lang="en">Hi to everyone,<br>
<br>
I would like to inform you that it's been almost one month since
Forthnet started dropping invalid prefixes on all peering/transit
links, either national or international. It's important to note
that during this month we haven't received any complaints.<br>
<br>
Having monitored the invalid prefixes for more than a year and
experimenting with routing them across different links, we decided
that it was time to move to the next phase and start dropping
prefixes that are declared as invalid in the RPKI ecosystem. <br>
<br>
Two were the main </span><span class="tlid-translation
translation" lang="en"><span class="tlid-translation translation"
lang="en">reasons that helped us take the drop decision: </span>a)
during the last year our volume of invalid prefixes traffic
decreased from ~1% of total traffic to less than 0,2%, b) we
updated our prefix validation policy by including a whitelist
(until we evaluate SLURM) in order to bypass issues quickly
if/when they arise.<br>
<br>
Note #1: in the context of the above actions we have noticed that
invalid prefixes </span><span class="tlid-translation
translation" lang="en"><span class="tlid-translation translation"
lang="en"> used for testing purposes </span>have recently begun
to grow (each large provider creates one?). This may lead to
incorrect conclusions in the future (at least in terms of
prefixes, since i don't expect traffic from those). Maybe these
invalid prefixes should have some extra "attributes" in order to
be recognized more easily while troubleshooting.<br>
<br>
Note #2: In order to increase adoption of a similar policy, maybe
MANRS should be updated to promote dropping invalids. If i'm not
mistaken, their current action is about creating ROAs only.<br>
<br>
--<br>
Tassos<br>
<br>
</span>
</body>
</html>