On 8/1/22 15:58, Ben Schwartz wrote:
On Mon, Aug 1, 2022 at 8:32 AM Independent Submissions Editor (Eliot
Lear) <[email protected] <mailto:[email protected]>> 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.
Note: .myfancymechanism is not currently registerable, and the
likelyhood is that it will take a few more years before it is. So new
TLDs aren't a *current* solution to anything.
However, myfancymechanism.info (or whatever existing, operational TLD
you prefer) is probably registerable, gives an unique prefix that is
guaranteed to conflict with zero names in the DNS, and can be
implemented without asking anyone.
The monetary cost of myfancymechanism.info above myfancymechanism.alt is
on the order of 10 dollars; the 10 dollars also gives you guarantees
about nobody else registering the same name in that space.
If "invoke the ICANN mechanisms" is an answer, then you're talking about
second level domains - cheap, available, and with no conflicts.
But they're not "special".
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".
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
