Hi, On Thu, Jun 27, 2013 at 11:53:46AM +0300, Andrey Semenchuk wrote:
So, speaking as router admin, my preference is to
- inform holders of objects with dangling references (admin-c, tech-c) - if nothing changes in, say, two weeks, inform LIR contacts as well - two weeks later, if the object is still referencing stale ASes, change object in DB, and again inform admin-c, tech-c, LIR contact
- reassign the no longer referenced AS
And your proposal is inconsistent with your example: the End User still can "restore reference to AS X inside AS Y object description during updating aut-num object"
Indeed. I want a light-weight process that can be implemented while it's still relevant (aka "we still have 16 bit ASNs to worry about"). The more heavyweight "full database consistency cross-check, including references to AS numbers that are not from the RIPE region(!)" needs to very carefully considered - if we make it too complicated to register policy, people will just stop doing so, and what have we gained then? Gert Doering -- Operator -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279