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

On Wed, Jun 26, 2013 at 12:06 PM, Richard Hartmann
<richih.mailinglist at gmail.com> wrote:

> There is no shortage of ASn so we have the luxury of being able to be _very_
> careful.

I now realized that this is mainly about 16 bit ASn.


> Even after an ASn had been reclaimed we can easily wait a significant period
> of time before recycling them.

And thus, this opinion changes.

I don't think anything should be changed by RIPE NCC, objects need to
be updated by their respective maintainers. In the best case, objects
are recreated from scratch locally whenever an update occurs,
rendering this moot. In the worst case, automated systems that do
Weird Things (tm) will malfunction in interesting ways.

Thus, I would think something along the lines of:

* When ASn is being deregistered, automatically email anyone who's
responsible for an object that references this ASn
* Once ASn is actually deregistered, send out automated email
* Once grace period is over, send out automated email
* Once ASn is reassigned, send final automated email

This means no effort on RIPE NCC's side, constant reminders to
operators who may either need time to find out what those emails mean
or under day-to-day stress (those exist, let's account for them), and
overall reasonable effort to clean something up that may never be
fully clean.

As to what time is appropriate, I am still unsure, but "short-ish".


Richard