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] Guidance Requested: Reassigning Referenced ASNs
- Previous message (by thread): [address-policy-wg] Guidance Requested: Reassigning Referenced ASNs
- Next message (by thread): [address-policy-wg] PA/PI unification IPv6 Address Space
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Charlie Allom
charlie at evilforbeginners.com
Mon Jul 1 15:47:22 CEST 2013
On Mon, Jul 01, 2013 at 02:55:44PM +0200, Elvis Velea <elvis at velea.eu> wrote: > > As far as I know, an AS Number can not be returned to the free > pool/deleted from the RIPE Database unless all referencing route > objects have been deleted. Any route object referencing a deleted AS > Number is a broken object and should be deleted. > > Therefore, the discussion here is not about references of returned > AS Numbers in route objects but more about references in other types > of objects (see below). Thanks for helping bring some clarity to this thread. > I think that publishing a list of referenced AS Numbers would be a > good first step in the clean-up. This way, any "concerned netcitizen > could parse the list and fix their records". Great idea. +1 C. -- 0x8486EDA8 http://spodder.com/
- Previous message (by thread): [address-policy-wg] Guidance Requested: Reassigning Referenced ASNs
- Next message (by thread): [address-policy-wg] PA/PI unification IPv6 Address Space
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]