[address-policy-wg] [db-wg] Guidance Requested: Reassigning Referenced ASNs

On 26/06/2013 19:11, Gert Doering wrote:
> which is exactly that sort of reference that would currently keep the
> NCC from reallocating AS48200 (assuming that one were free).

... which is why I suggested that inaction shouldn't negatively affect
timelines.  People never clean up after themselves, so the RIPE NCC will
either need to edit the affected objects themselves (which will work fine
until someone's provisioning database respams the DB with out-of-date
information) or else notify + wait, but then ultimately ignore if there's a
problem.  Other IRRDBs are other peoples' problems.

A recycling period of a couple of months would seem sensible, as there will
be a resource shortage for asn16s.  There's no reason for the RIPE NCC not
to notify references immediately.

Nick