Re: [DNSOP] Questions on draft-ietf-dnsop-delegation-only

[Hugo Salgado <[e-mail]>]

On 16:55 30/07, Patrick Mevzek wrote:
> 
> Only if you take the "hosts as objects" case (where any hosts to be used as
> to be provision like a domain but by just providing, in some cases, some IP
> addresses), which is only one of the two, the other being "hosts as
> attributes (of a domain object)"
> 

.CL uses "hosts as attributes".

> There are various solutions, all bad in some aspects:
> 
[...]
> - have the registry let the domain be deleted and then have domainB be
> broken (which it is already in a way since the delegations to those
> nameservers can be explicitly made broken; but the difference is between
> registrar A breaking registrar B stuff, or the registry breaking registrar B
> stuff).

And this approach. When DomainA is deleted/deactivated, its
nameservers are gone in the .cl zone, together with their
glues. Nameservers ns1.domainA.example and ns2.DomainA.example
are deleted from DomainB's NS set too, because there's no DomainA
anymore... and so we keep .cl consistency.

So we can say .CL is truly delegation-only. But we know there're
only a handful of registries using hosts-as-attributes.

Hugo