Re: [dnsext] I-D Action:draft-ietf-dnsext-aliasing-requirements-00.txt

[Alex Bligh <[e-mail]>]

--On 28 February 2011 09:48:59 +0100 Stephane Bortzmeyer 
<[e-mail]> wrote:

>> > technology; it can be done, and is done today, entirely with
>> > provisioning logic and registry policy.
>>
>> +AB: Note this isn't only a registry solution. It could be done by
>> +AB: users too (e.g. through a zonefile preprocessor that was
>> +AB: run prior to signing of the zone).
>
> A registry can be at any level. See the IDN RFCs which use the word
> "registry" for "anything that manage a zone, whether the zone is .com
> or foobar.momandpop.example".

I'm not sure that's the natural meaning of the term, nor that
that's how the draft uses it, e.g. from Section 5 in the I-D

>    In
>    addition, as described briefly above, registry operators have a great
>    many techniques for applying policy to what names can be registered,

but if we going to use "registry" to mean "zone manager", we should
say so. Otherwise, we should just say "zone manager" where it's
applicable to more than registries (meaning ones allowing third
party registrations).

-- 
Alex Bligh