> On 17 Apr 2025, at 20:47, David Conrad <d...@virtualized.org> wrote:
>
> My understanding is that ICANN (or anybody) needs IETF approval to modify
> https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml.
> If that’s not the case, “never mind”.
>
> I just think the reliance on lore and oral tradition as opposed to SDO
> documented specifications to properly develop/operate the DNS should be
> avoided.
I agree with that 100%. ie Nothing goes into that IANA registry unless it's
supported by an RFC which documents why the string truly is special. For some
definition of special.
IMO, the .internal TLD isn't special => IETF shouldn't be rubber-stamping its
addition to the above IANA registry. That way lies madness. It'll drag the IETF
into all sorts of layer-9+ ugliness that has little to do with engineering or
protocol matters: "Since you've put .internal on this registry, the IETF must
now do that for .hisjimness because $reasons" or "add names for every
flavour-of-the-month cryptocurrency/blockchain scheme that comes along because
the proponent claims these are special too".
If ICANN (or anyone else) needs a registry of special TLDs that won't go in the
root or can't ever be sold, they are free to do that - all by themselves. IMO,
they don't need to come knocking on the IETF's door. More so when the
choice/use of special TLD strings are driven by considerations which have a
marginal (at best) engineering basis or have no significant impact on the
stability of the Internet.
Taking .internal as a case in point, we've got along just fine for 20+ years
without having this name in the IANA special use registry. No doubt we'll get
along just fine for at least than long if it still isn't there. So why bother?
In a nutshell, here's my question. What's the technical/engineering
justification for the IETF to add .internal to the IANA special use registry?
How does that make things better (or stop them getting worse)? OK, that's 2
questions. Sue me. :-)
_______________________________________________
DNSOP mailing list -- dnsop@ietf.org
To unsubscribe send an email to dnsop-le...@ietf.org
