Re: [DNSOP] Alternative Special-Use TLD problem statement draft

["Adrien de Croy" <[e-mail]>]

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" <[e-mail]>
To: "Philip Homburg" <[e-mail]>
Cc: "[e-mail]" <[e-mail]>; "Ted Lemon" 
<[e-mail]>
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 <[e-mail]> 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
>[e-mail]
>https://www.ietf.org/mailman/listinfo/dnsop