Gert Doering <gert@space.net> schrieb:
Hi,
On Thu, Jun 27, 2013 at 09:51:56AM +0300, Andrey Semenchuk wrote:
On 06/27/13 01:52, Andreas Schachtner wrote:
Sanity checking upon submitting to the DB could prevent this.
And it's the main problem that we should talk. But not about removing
some references to the objects that doesn't exists The lack of sanity check for the corresponding fields during database
updates - is the root of the problem.
It's not the *root* of the problem, but just one aspect (when the AS number is returned, all references to it are perfectly fine, up to that point) - and even then, you can't really solve the whole issue with technical means.
Consider this:
AS X is returned AS Y references it, database object is changed by NCC to remove reference to X <two month pass> AS X is reassigned to someone else AS Y sends an update to it's aut-num: object, restoring the reference to X
now what - is this "illegal" because it's "an old reference", or should this be permitted, because it's really referencing to "the new holder of X"? (we can't know, so technical "blocking" of references to X will do the wrong thing in half the cases...)
The sanity check could and should check if the inverse exists. And any import in aut-num X for asn Y that has no export in aut-num Y within 2 days has to be treated as illegal and removed, notifying the holder. And as some people only react when it hurts, I would even charge the removal if it happens more than once ... Also exports/imports as for example seen in aut-num 3320 (from any import any; to any export any) should be treated as illegal! Jens
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
(speaking for myself and my routers, not speaking as WG chair)
Gert Doering -- Operator
-- Jens Ott Opteamax GmbH Simrockstr. 4b 53619 Rheinbreitbach Tel. +49 2224 969500 Email: jo@opteamax.de HRB 23144, AG Montabaur