Creation of Reverse Delegation Objects

Dear Wilfried,

I wholeheartedly agree with your arguments:

There *IS* indeed a mandate on the RIPE NCC to provide services to the
community at large. The RIPE Database is a fine example. However, the handling of
the in-addr tree is a membership service and as such only available to
members of the RIPE NCC Association.

I agree with the fact that old hats usually have greater knowledge than
new hats (though not always). Those are usually either LIRs or have their
address space registered at the ARIN Database (and yes this becomes an
issue to discuss in view of the pending transfer of "legacy" space from
ARIN to the RIPE NCC).

I agree with the fact that the RIPE NCC should not change things
unilaterally and without discussion
(though we should not become inoperative). However Tanja is the one
requesting the change. The RIPE NCC hasn't changed the behaviour of the
in-addr robot for longer than I have been here (and that's about 50% of
the RIPE NCC's life already)

I agree that you don't want things like this to be put into a wait queue.
The in-addr robot has nothing to do with any wait queue. If the command is
sent correctly no hostmaster ever looks at the request. The robot analyzes
it, does the DNS checks and registers the new set of name servers in the
RIPE Database (assuming all is OK). Most of the requests get done that
way, without human intervention. Having the reg.id enables the robot to
check whether the requester is a member or not.

I also agree that Dominic's mail might have been a bit oversimplified,
probably from the fact that a lot of context was taken for granted.

I hope to have filled you in with this message

Regards,
joao