This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/routing-wg@ripe.net/
[routing-wg] RIS dumps, 0.0.0.0/0 routes and RPKI validator 3
- Previous message (by thread): [routing-wg] RIS dumps, 0.0.0.0/0 routes and RPKI validator 3
- Next message (by thread): [routing-wg] RPKI validator 3: initial sync regression?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Rene Wilhelm
wilhelm at ripe.net
Mon Mar 18 03:08:40 CET 2019
On 3/16/19 11:57 PM, nusenu wrote: [...] > > Are 0.0.0.0/0 routes filtered by RIPEstat but > included in RIS dumps? > Should rpki-validator filter them out? In the bgp-preview? Probably. Although the route is in RIS, provided by some peers, 0.0.0.0/0 does more harm than good in tools like RIPEstat and the rpki-validator's preview. Alternatively, developers could raise the lower limit of number of RIS peers which must see a route before it is included in the preview. Currently, that limit is set to 5. The 0.0.0.0/0 routes typically have very low visibility. The latest dump at http://ris.ripe.net/dumps/riswhoisdump.IPv4.gz sees 0/0 announced by 24 different ASes. But where most of them are seen by just 1, 2 or 3 out of 222 full feed RIS peers, the announcement by AS15576 is seen by 5 peers and thus makes it to the preview. -- Rene
- Previous message (by thread): [routing-wg] RIS dumps, 0.0.0.0/0 routes and RPKI validator 3
- Next message (by thread): [routing-wg] RPKI validator 3: initial sync regression?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]