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] Bogon ASN Filter Policy
- Previous message (by thread): [routing-wg] Bogon ASN Filter Policy
- Next message (by thread): [routing-wg] The Cidr Report
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
heasley
heas at shrubbery.net
Tue Jun 14 23:46:20 CEST 2016
Tue, Jun 14, 2016 at 04:51:40PM +0300, Alexander Azimov: > But I have security consideration that filtering isn't a proper mechanism > to reach this goal. Imagine next situation - if transit accidently prepends > its paths with private AS number it will result in DoS for all stub > networks connected to this transit. I think, better way is deprioritize > bogon routes - this will stop propagation of such routes if there is any > alternative and will not affect reachability in other cases. These should not appear in the DFZ. I can think of no better way to encourage resolution than dropping such routes.
- Previous message (by thread): [routing-wg] Bogon ASN Filter Policy
- Next message (by thread): [routing-wg] The Cidr Report
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]