Just speaking as an author, I (1) acknowledge your point, with which I agree and (2) point out that what Philip described is nonetheless a problem that ought to be mentioned in the problem statement, because cleaning up after such a registration has been done is actually a hard problem, and so we want to make sure that whatever solution we propose gives people a better way to solve the initial registration problem so that they _don't_ register what they intend to be a special-use name under some TLD using the normal TLD registration process.
On Wed, Apr 6, 2016 at 8:52 AM, Stephane Bortzmeyer <[email protected]> wrote: > On Wed, Apr 06, 2016 at 01:17:00PM +0200, > Philip Homburg <[email protected]> wrote > a message of 43 lines which said: > > > In fact, there is quite a bit of history already in some programming > > languages (for example java) to just register a DNS domain to get a > private > > part of the global name space. > > > > 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. You depend on the registry's policy, which may suit > you or not, and, if the registry uses RRR, you depend on the > registrar's behavior. One mistake by Go Daddy or Network Solutions and > you lose your namespace. One complaint to a private "court" such as > UDRP and you lose your namespace. > > It may work for a big company like Sun with a lot of lawyers. It does > not for the typical free software project such as .onion or the people > in the queue (.gnu, .bit, etc). > > _______________________________________________ > DNSOP mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dnsop >
_______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
