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]/
[routing-wg] [db-wg-chairs] ASN reference cleanup
- Previous message (by thread): [routing-wg] [db-wg-chairs] ASN reference cleanup
- Next message (by thread): [routing-wg] [db-wg-chairs] ASN reference cleanup
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wilfried Woeber
Woeber at CC.UniVie.ac.at
Thu May 15 18:55:53 CEST 2014
Rob Evans wrote: > Hi, > > >>my point of view as a DB-Co-chair (at the moment) is that we don't need a >>formal policy, if the problem is well understood, we do have a sound proposal >>how to move forward and there is no severe impact on daily operations for the >>users of the DB services; (and no substantial disagreement). > > > For those who weren't present in the routing working group this afternoon, > either physically or virtually, there was a strong sentiment that the RIPE > NCC should *not* edit other objects to remove references to reclaimed ASNs. > > Send out warnings, by all means, but editing other objects would open up a > can of worms that is best left sealed under pressure. Thanks for this feedback, noted! Wilfried. > Cheers, > Rob >
- Previous message (by thread): [routing-wg] [db-wg-chairs] ASN reference cleanup
- Next message (by thread): [routing-wg] [db-wg-chairs] ASN reference cleanup
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]