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]/
[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 ]
Andrey Semenchuk
andrey at trifle.net
Thu Jun 27 08:51:56 CEST 2013
On 06/27/13 01:52, Andreas Schachtner wrote: > Sanity checking upon submitting to the DB could prevent this. And it's the main problem that we should talk. But not about removing some references to the objects that doesn't exists The lack of sanity check for the corresponding fields during database updates - is the root of the problem. +1 > Auto-cleaning the route: objects still referencing AS48200 is fairly > easy, but auto-cleaning export/import policies and AS-SET objects is > harder, especially as people might have the aut-num: object in > question on file, just change stuff locally, and then re-send it when > they have changes, overriding the cleaned-up object in the database... -- Best wishes, Andrey Semenchuk Trifle Internet Service Provider (056) 731-99-11 www.trifle.ne
- 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 ]