Re: [db-wg] Adequate contact information in the RIPE database must be enforced (was: NCC#2008090071 Unreachable Italian Host)
-
To: Shane Kerr shane@localhost
-
From: Marco Hogewoning marcoh@localhost
-
Date: Wed, 3 Sep 2008 21:00:54 +0200
-
Cc: Thor Kottelin thor@localhost, db-wg@localhost
On Sep 3, 2008, at 1:36 PM, Shane Kerr wrote:
There are a couple of problems with this though:
1. It costs money, both on the side of the NCC and the contact.
2. There is no enforcement mechanism.
I would be happy for the NCC to spend money on this, but I don't
represent an LIR. ;)
I do and I'm happy to support and even co-author a proposal about
something like this. But at this point in time I can't think of any
working solution as we indeed lack the tools to enforce.
For resources allocated or assigned to an LIR, this should be pretty
straightforward. Every LIR pays a fee each year, after all!
For other resources (PI blocks and AS numbers) it is more difficult,
since there is no established relationship with anyone(*). But, it is
still possible to look at the routing tables and contact peers to
figure
this out, with some work.
It basically also goes for PA, escpecially large LIR's usually can
have multiple role accounts and not every country/department keeps
their info accurate. And then of course theirs the group who actually
put contacts in for the customer using the space.
If you go upstream to the allocations I think the organisation object
can be pretty accurate as it's also used for certain communications
between the LIR and NCC but I can imagine you want a more fine grain.
This is probably more something for the services working group.
Agree...
MarcoH
|