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] Our AS is in a macro that we don't authorize.
- Previous message (by thread): [members-discuss] Our AS is in a macro that we don't authorize.
- Next message (by thread): [members-discuss] Our AS is in a macro that we don't authorize.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tore Anderson
tore at redpill-linpro.com
Fri Nov 2 09:32:24 CET 2018
* José Manuel Giner > Hi, we checked that our AS is present in the macro: AS24748:AS-THINX > (they have thousands of AS in their macro) > We are concerned about this situation and do not know how to proceed. To the best of my knowledge, there exists no mechanism in the database that lets ASN holders to authorise or deny the inclusion of their ASN in someone else's AS-set. For example, nobody can stop me from creating AS-set «AS-ALL-ODD-ASNS» containing AS1,AS3,AS5, et cetera. And nobody can stop me from instructing my peers and upstreams to use that AS-set to build their route filters facing my AS. This facilitates hijacks by malicious actors, of course. RPKI won't help as the origin AS is easily spoofed. You are of course free to attempt to chase down the maintainers of the offending AS-sets and convince them to remove your ASN, but over time it likely becomes an exercise in futility. C'est la vie... Tore
- Previous message (by thread): [members-discuss] Our AS is in a macro that we don't authorize.
- Next message (by thread): [members-discuss] Our AS is in a macro that we don't authorize.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]