Re: [DNSOP] I-D Action: draft-ietf-dnsop-delegation-only-00.txt

[Paul Wouters <[e-mail]>]

On Wed, 6 May 2020, Ray Bellis wrote:

> §8 of the draft says:
>
>> Some TLDs have a requirement for certain Fully Qualified Domain Names
>> (FQDN) within their TLD, such as "whois.example" or "nic.example".
>> These usually appear as signed data of the TLD and not as a delegated
>> child zone.  These names would have to be converted to delegated
>> zones before enabling the DELEGATION_ONLY flag
>
> Requiring such records to become delegations may be impossible if the
> existing names (that might now become apex records) require a CNAME.

Why would this _require_ to be a CNAME ?

If whois.example. is now a CNAME to somewhere.something.example. then
you could setup a new zone for whois.example. You are saying the tools
cannot set the A/AAAA records of this new zone to point to the old
CNAME? Or you are afraid the "CNAME update procedure" cannot be
easilly ported to a "A/AAAA update procedure" ?

I would say that a TLD should probably be capable of handling this.

> Another non-delegation record also commonly found in TLDs is
> _nicname._tcp.<tld> SRV.

_underscore labels are excempted in the draft already, because it is
understand that these really always apply to the zone itself, and
are never valid delegations to other entities.

Paul