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/[email protected]/
[members-discuss] [Ticket#2012061901001911] Need help. Can't remove routes for ex Assigned PA.
- Previous message (by thread): [members-discuss] [Ticket#2012061901001911] Need help. Can't remove routes for ex Assigned PA.
- Next message (by thread): [members-discuss] [Ticket#2012061901001911] Need help. Can't remove routes for ex Assigned PA.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sascha Lenz
slz at baycix.de
Tue Jun 19 15:06:20 CEST 2012
Hi, > You could announce the /24 and 2 * /25 yourself and blackhole to reduce > the impact, not everyone filters on /24. please don't pollute the DFZ. Contacting the (other) upstreams and tell them the route is bogus is the only intelligent option. If the inetnum object is removed, they can see the announcement is not valid in the first place. Everything else has been said already, just don't use PA like that. I'm not sure what would be the proper way to get the route object removed in this case either. -- Mit freundlichen Grüßen / Kind Regards Sascha Lenz [SLZ-RIPE] Senior System- & Network Architect
- Previous message (by thread): [members-discuss] [Ticket#2012061901001911] Need help. Can't remove routes for ex Assigned PA.
- Next message (by thread): [members-discuss] [Ticket#2012061901001911] Need help. Can't remove routes for ex Assigned PA.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]