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/address-policy-wg@ripe.net/
[address-policy-wg] [db-wg] Guidance Requested: Reassigning Referenced ASNs
- Previous message (by thread): [address-policy-wg] [db-wg] Guidance Requested: Reassigning Referenced ASNs
- Next message (by thread): [address-policy-wg] [db-wg] Guidance Requested: Reassigning Referenced ASNs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Erik Bais
erik at bais.name
Wed Jun 26 22:16:41 CEST 2013
Hi Andrey,
You stated (if I may quote you freely) ... that if an AS number is returned, it might / should not impact routing ...
And you are probably right for 99.8% ..
However ... there might be situations where someone would be using a certain BGP community in RPLS for internal reference still while the actual AS number isn't used anymore.
Think about a similar way as how certain routeserver filtering is implemented.
import: from AS6777 action pref=85; accept ANY AND NOT <^[ASAAAA ASXXXX ASYYYYY ASZZZZZ ASWWWW]> AND NOT {0.0.0.0/0}
export: to AS6777 action community .= {6777:6777, 6777:AAAAA, 6777:XXXX, 6777:YYYYY, 6777:ZZZZ, 6777:WWWW}; announce AS-<as-number>
Erik Bais
- Previous message (by thread): [address-policy-wg] [db-wg] Guidance Requested: Reassigning Referenced ASNs
- Next message (by thread): [address-policy-wg] [db-wg] Guidance Requested: Reassigning Referenced ASNs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]