[ncc-services-wg] Reverse DNS Restructuring Project

Olaf,

On Wed, Oct 01, 2003 at 05:39:28PM +0200, ext Olaf M. Kolkman wrote:
>  
>   - The introduction of a new attribute, "mnt-domains:", in INETNUM and
>     INET6NUM objects to be able to delegate the authority to create
>     new domain objects.

Does this mean that the 'rev-srv:' attribute will be retired too ?!?

This proposal also means that one has to submit for example 16 reverse
delegation objects to do a reverse delegation of a single /20.

I was the one who wrote the first 'reverse delegation checking tool'
for the RIPE NCC a long time ago and we used the 'domain:' object
approach because that was 'the way it was always done' but it still
doesn't make a lot of sense to me.

Would it not be more customer friendly to find a way to allow people to
request for the reverse delegation of a block of IP addresses,
no matter what the size of the block actually is ?!?

Unfortunately, reverse delegations are (generally) done on 8 bit
boundaries but I don't see much reason why we should expose this
kludge to the user (and neither do ISPs who use a good configuration
system for their DNS servers). Adding a couple of 'rev-srv:'
attributes to one 'inetnum:' object seems so much easier to me.

In fact, there is actually very little use for doing the whole thing
in the RIPE database in the first place. I haver never found any use
at all for looking up one of the in-addr.arpa objects in the database.
Maybe we should even think about retiring the 'domain:' objects and
'rev-srv:' attributes altogether and offer a simple secure web or mail
user interface for submitting reverse delegations.

David K.
---