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 ]
José Manuel Giner
jm at ginernet.com
Fri Nov 2 10:27:09 CET 2018
I want my traffic routed where I want it. I'm not a member of that IX and if you're routing traffic through this IX, it's being a latency problem (my servers are a far away from that IX, +60 ms) and possibly a hijaking security problem. On 01/11/2018 10:13, Tapio Haapala wrote: > Why you want remove your AS from IX routing list? You want that your > prefixes does not get routed to some part of internet? Correct if I am > wrong but for me that looks more like that at least someone (atman) do > filtering even for tier1 operators and at least in theory it should be > good thing. > > > On 30.10.2018 16:27, José Manuel Giner wrote: >> Hi, we checked that our AS is present in the macro: AS24748:AS-THINX >> (they have thousands of AS in their macro) >> >> After contacting atman.pl who is responsible for this macro, they tell me: >> >>> It appears that AS59432 is contained in one of our customers AS-SETs and >>> it is automatically added to our AS-SET AS24748:AS-THINX >>> >>> As soon as they remove AS59432, it will disappear from AS24748:AS-THINX >> >> We have asked him how we can find out who that customer is. But their >> answer doesn't give us any information. >> >>> Please be kindly informed that our macros are being built automatically >>> according to our customers` macros. If your AS happens to be removed >>> from whichever of our customer`s macros, ours is to be changed >> accordingly. >> >> We are concerned about this situation and do not know how to proceed. >> >> Thank you for your help! >> > > -- José Manuel Giner http://ginernet.com
- 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 ]