in-addr.arpa zone data in RIPE database

> An indirect way of correcting things via submissions to the RIPE DB in my
> view is far from ideal, as it may well introduce unnecessary delays.

Soon this argument will be moot for at least 193.in-addr.arpa...

> And once you start doing such things for the reverse servers, the next
> step may well be doing the same for "forward servers"; then how can e.g.
> a top level domain registrar determine whether a given change is valid,
> e.g. comes from an authoritative person?

Call (ie. phone) the supplied administrative contact person?  How do you
ensure authority today?

- Havard