On Wed, Feb 07, 2007 at 08:34:28PM +0100, Philippe Bourcier wrote:
A few months ago I tried to start a thread on db-wg about the IRT
object use and ease of deployment and had not much success... so I
hope it will get more success here.
As I already wrote back in Sep. 2004:
What I really don't understand is why this information has to be in the
RIPE database.
The DNS RR "RP" (Responsible Person) is there sind October 1990
through RFC 1183.
For examples see (at my former employer)
$ dig 30.195.in-addr.arpa rp
$ dig 1.30.195.in-addr.arpa rp
or even (customer webserver)
$ dig 1.249.30.195.in-addr.arpa rp
Not 100 different whois databases with 90 different access methods.
One clear, well defined interface for all in a distributed, hierarchical,
replicatable database with caching, referral and aliasing capabilities ;-)
And one can specify responsibility down to a single IP address. And
authorization to edit the records comes directly from delegation and
write access to the reverse zone file.
Propagation is fast and easy, for starting just add 1 (one!) record to
the (e.g. /24) zone:
BIND:
@ IN RP abuse.example.com. .
Done. No WG discussion, no software modifications, it simply works.
Immediately.
<sarcasm>
I know the solution is unkewl ... instead of spending more than 2.5 years
with discussions and not get anything done it is too lame to spend 2
minutes
time and simply make the f*cking entry and get things working.
Using things that exist for years and work and not reinventing the wheel
the 10th time and not to spend months on testing, debugging and software
development is simply too lame these days.
</sarcasm>
\Maex
