Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns-alt-tld

[Ben Schwartz <[e-mail]>]

On Mon, Aug 1, 2022 at 8:32 AM Independent Submissions Editor (Eliot Lear) <
[e-mail]> wrote:
...

> I do agree with Martin that it would be helpful to have some registration
> of names so that conflicts between name spaces can be avoided.
>
I think we already have such a mechanism: ICANN.  People who want unique
registrations can acquire them via the existing ICANN and registry
processes.

I do not think that the IETF should introduce another mechanism for third
parties to acquire non-conflicting domain names.  Any such mechanism would
appear to compete with ICANN and the registries, without the benefit of
ICANN's extensive, hard-won process and governance.

> This would also encourage formal documentation of those projects.
>
This raises the interesting question of when use of non-ICANN registration
is appropriate.  I think RFC 6761 has the right answer: "Standards Action
or IESG Approval".  In other words, the IETF should only be taking control
of DNS namespaces that correspond to IETF standards-track protocols, with
an escape hatch via the IESG for special situations.

Projects that need a non-ICANN domain name can seek IETF standardization,
which represents both formal documentation and consensus that this use
constitutes "part of the internet itself".