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

"Adrien de Croy" <adrien@qbik.com> Thu, 07 April 2016 20:34 UTC

Return-Path: <adrien@qbik.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8794612D65D for <dnsop@ietfa.amsl.com>; Thu, 7 Apr 2016 13:34:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id of8_cgbCjwDQ for <dnsop@ietfa.amsl.com>; Thu, 7 Apr 2016 13:34:48 -0700 (PDT)
Received: from smtp.qbik.com (smtp.qbik.com [122.56.26.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5AA7C12D175 for <dnsop@ietf.org>; Thu, 7 Apr 2016 13:34:48 -0700 (PDT)
Received: From [192.168.1.146] (unverified [192.168.1.146]) by SMTP Server [192.168.1.3] (WinGate SMTP Receiver v8.5.6 (Build 4877)) with SMTP id <0000693533@smtp.qbik.com>; Fri, 08 Apr 2016 08:34:46 +1200
From: Adrien de Croy <adrien@qbik.com>
To: David Conrad <drc@virtualized.org>, Philip Homburg <pch-dnsop@u-1.phicoh.com>
Date: Thu, 07 Apr 2016 20:34:45 +0000
Message-Id: <em14138875-628b-4b38-9cf7-6ba7756e6079@bodybag>
In-Reply-To: <2B9797D2-C3DF-471F-9440-26943A744095@virtualized.org>
User-Agent: eM_Client/6.0.24928.0
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="------=_MBE477AB23-4D25-4142-B8DA-23F6890FA9B9"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/S5fgDLOlZ-qnYKpXcCdB6acbYZI>
Cc: "dnsop@ietf.org" <dnsop@ietf.org>
Subject: Re: [DNSOP] Alternative Special-Use TLD problem statement draft
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Adrien de Croy <adrien@qbik.com>
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Apr 2016 20:34:50 -0000

------ Original Message ------
From: "David Conrad" <drc@virtualized.org>
To: "Philip Homburg" <pch-dnsop@u-1.phicoh.com>
Cc: "dnsop@ietf.org" <dnsop@ietf.org>
Sent: 8/04/2016 12:38:26 a.m.
Subject: Re: [DNSOP] Alternative Special-Use TLD problem statement draft

>Philip,
>
>On Apr 7, 2016, at 7:57 AM, Philip Homburg <pch-dnsop@u-1.phicoh.com> 
>wrote:
>>  However, having lived through a period where many different naming 
>>systems where
>>  use in parallel and seeing what benefits it brought to have to 
>>consider just DNS,
>>  I think a model where IETF and ICANN actively control the consistency 
>>of the
>>  internet name space is best.
>
>I do not believe IETF or ICANN have that level of control. The Internet 
>is known for "permissionless innovation" for a reason.
>
>>  I have created naming systems myself. And there are many reasons to 
>>dislike
>>  DNS and do something different.
>
>Right.
>
>>  But ultimately, for the stability of the internet, it is best to not 
>>do that.
>>  Write some experimental code, write a few papers and be done with it. 
>>Then,
>>  if you still care about the problem, work within the IETF to improve 
>>DNS.
>
>I believe the point of the special use registry is that these are 
>protocols that are not DNS and have no interest in being in the DNS, 
>but which make use of domain name conventions.  The alternative to the 
>special use registry is not that such names won't exist, rather it is 
>that the names will collide with names in the DNS.
>
>
>

the question is whether we should fundamentally change the domain name 
system to accommodate this or not.  My position is we should not.

Just because TOR asks for .onion doesn't mean it should be given it.

I understand the IETF is supposed to obtain consensus, but I didn't see 
anything in http WG on this until after the fact.  Special use names has 
wide-ranging repercussions.

If an author of a product chooses to devise a new non-dns resolution 
mechanism, and use names that are confusingly similar to domain names, 
and use names that may be issued by ICANN in the DNS, then I'm sorry but 
they need to look for an alternative technical solution.  Not make 
everyone else in the world change to suit them.

Regards

Adrien


>
>
>Regards,
>-drc
>(speaking only for myself)
>