On 8/13/22 11:57, John R Levine wrote:
That said, I believe what Warren is suggesting is more of a ten thousand foot
view of the namespaces issue; and if that finds a way to allow innovation
without fragmentation, it would be beneficial for DNS and non-DNS names alike.
That would be swell, but since we've been wrestling with this problem for 25
years and have made no progress, I don't think a few more rounds is likely to
provide a breakthrough.
It's not a technical problem, it's a social or political one. People have
projects outside the DNS and want to name them with DNS names. Sometimes you
can't have what you want.
The issue is *precisely* that they want dotted *names*, *not* DNS names, but
there is overlap in namespace.
I don't think it's accurate to claim that anyone who wants to use a
dot-separated namespace wants a DNS name. For the misunderstandings it creates,
I'd suggest changing the framing.
With this distinction in mind, the problem of non-DNS names is not within the
remit of the DNS name allocation folk (ICANN). (Unlike the .internal DNS name.)
"Disentangling namespace" and coming up with related proposals/conventions (or
giving up) is on the protocol folk (IETF).
Warren is trying to motivate continuing the discussion among those who are
interested, for which he is planning to create some venue. I think that's fair
for the group of people who wants to talk about that.
I'm not implying that protocol folk could actually find a solution. I don't
know that. From a 1000-ft perspective, perhaps no solution exists. But I see no
problem with having a (non-DNS) list on which that is discussed.
Thanks,
Peter
--
https://desec.io/
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
