[db-wg] IRT object creation is easy

Hi Jeroen,



> > Im sure that creating an IRT object is doable for any ISP
> > which takes the time. The reason why I do not wish to use
> > IRT is that it is much too complex
> > for the very simple purpose it should have. It seems to have
> > been designed to be used for outsourcing of abuse-handling,
> > Im sure some ISP's do this but
> > I haven't yet seen any numbers which justifies a design which
> > primarily favors these ISP's.
>
> It is a seperate object, just like what the abuse-c is supposed
> to be, but indeed without the encryption. If you put one pgpkey
> in the RIPE registry you are done, and you should already be
> using signed messages to update your objects anyways.

When creating a non-IRT object the encryption in the maintainer is used..
Why can't it be the same with IRT?

>
> > Remove the encryption-thing on the IRT object and let it be
> > maintained by a maintainer object, then Im sure more ISP's
> > would be willing to implement it,
> > but for it to become a success I still believe the designers
> > need to pay attention to the needs of those ISP's who have
> > no use for the current version.
>
> I could live with changing the mnt-irt to be an or case with
> the mnt-by too indeed as currently when one wants to update
> an object protected by the mnt-irt it needs to be signed by
> both the mnt-by and the mnt-irt, when you are 'outsourcing'
> as you call it this is a problem, otherwise one will have
> access to both the maintainer and the irt anyhow.
>
> > I think its very unfortunate that the Ripe DB doesn't have
> > abuse information on all IP addresses, that should actually
> > be the primary goal for a public
> > IP database, at least from the Internet users perspective.
>
> Well currently, according to toolwriters, it has, as they will
> just use all the e-mail lines they can find.
> Now there is a good solution, not ;)

Well, the easy solution would have been to just put a mandatory abuse-email
on the maintainer object, this would force all inet(6)num's to instantly
have an abuse address - setting the notify address as default or similiar
will also encourage LIR's to change the abuse address to the correct one.

Of course this might be a bit too simplified, but I still believe the most
important is to have an abuse address associated with each IP address in the
Ripe DB as soon as possible.



Med venlig hilsen/Best regards

Christian Rasmussen
Hosting manager, jay.net a/s

Smedeland 32, 2600 Glostrup, Denmark

Email: noc at jay.net
Personal email: chr at corp.jay.net
Tlf./Phone: +45 3336 6300, Fax: +45 3336 6301

Produkter / Products:
http://hosting.jay.net