Why do DNS programmers need to care about these "special" names in the
normal domain name space?
The question is what protocol to use.
I think we still need to answer the question about whether DNS namespace
should be polluted for non-DNS resolution.
------ Original Message ------
From: "Stephane Bortzmeyer" <bortzme...@nic.fr>
To: "Philip Homburg" <pch-dn...@u-1.phicoh.com>
Cc: "dnsop@ietf.org" <dnsop@ietf.org>; "Ted Lemon"
<ted.le...@nominum.com>
Sent: 7/04/2016 12:21:31 a.m.
Subject: Re: [DNSOP] Alternative Special-Use TLD problem statement draft
On Wed, Apr 06, 2016 at 08:52:43AM -0300,
Stephane Bortzmeyer <bortzme...@nic.fr> wrote
a message of 21 lines which said:
> So anybody who wants to play with an experimental naming service
can just
> register my-naming-service.net. And use that string in any name
switch code.
Strong dissensus here. The problem is there is no safe way to have
AND
KEEP such a name.
Also, it would make very difficult to DNS programmers to keep track of
all these "special but not special" domain names. Some people
complained that it was difficult enough with RFC 6761 (because there
is no machine-readable version of the special-use registry) but it
would be worse with scattered domain names in many TLDs.
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
