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/address-policy-wg@ripe.net/
[address-policy-wg] [db-wg] Guidance Requested: Reassigning Referenced ASNs
- Previous message (by thread): [address-policy-wg] [db-wg] Guidance Requested: Reassigning Referenced ASNs
- Next message (by thread): [address-policy-wg] [db-wg] Guidance Requested: Reassigning Referenced ASNs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Thu Jun 27 09:59:26 CEST 2013
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...)
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
--
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 306 bytes
Desc: not available
URL: </ripe/mail/archives/address-policy-wg/attachments/20130627/f3e1beba/attachment.sig>
- Previous message (by thread): [address-policy-wg] [db-wg] Guidance Requested: Reassigning Referenced ASNs
- Next message (by thread): [address-policy-wg] [db-wg] Guidance Requested: Reassigning Referenced ASNs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]