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

Philip Homburg <pch-dnsop@u-1.phicoh.com> Thu, 07 April 2016 10:57 UTC

Return-Path: <pch-bBB316E3E@u-1.phicoh.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 A833E12D6EE for <dnsop@ietfa.amsl.com>; Thu, 7 Apr 2016 03:57:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 RGSNjyPyegsm for <dnsop@ietfa.amsl.com>; Thu, 7 Apr 2016 03:57:36 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6-he.hq.phicoh.net [IPv6:2001:470:d16a:10:2a0:c9ff:fe9f:17a9]) by ietfa.amsl.com (Postfix) with ESMTP id 6DE7212D6E1 for <dnsop@ietf.org>; Thu, 7 Apr 2016 03:57:34 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #91) id m1ao7cz-0000DxC; Thu, 7 Apr 2016 12:57:33 +0200
Message-Id: <m1ao7cz-0000DxC@stereo.hq.phicoh.net>
To: dnsop@ietf.org
From: Philip Homburg <pch-dnsop@u-1.phicoh.com>
Sender: pch-bBB316E3E@u-1.phicoh.com
References: <8D23D4052ABE7A4490E77B1A012B630797A44227@mbx-03.WIN.NOMINUM.COM> <m1anlSH-0000IqC@stereo.hq.phicoh.net> <20160406115243.GA14413@laperouse.bortzmeyer.org> <20160406122131.GA15698@laperouse.bortzmeyer.org> <m1anp1K-0000CzC@stereo.hq.phicoh.net> <FE146F00-3663-4042-9E41-ED62D0DB64DA@virtualized.org>
In-reply-to: Your message of "Wed, 6 Apr 2016 21:52:59 -0300 ." <FE146F00-3663-4042-9E41-ED62D0DB64DA@virtualized.org>
Date: Thu, 07 Apr 2016 12:57:32 +0200
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/_72FKg6IKg8DnlS2kT34fO-lct4>
Cc: David Conrad <drc@virtualized.org>
Subject: Re: [DNSOP] Alternative Special-Use TLD problem statement draft
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
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 10:57:38 -0000

>> There should be no register, because they should not exist.
>
>This appears to assume that naming systems are only developed in the 
>IETF or that a naming system not developed in the IETF is not 
>relevant/impactful.
>
>I don't think this is a good assumption.

To be more specific. In my opinion, the IETF should not reserve any names for
for naming systems developed outside the IETF. 

Obviously, anybody is completely free to develop a naming system outside the
IETF. And obviously any operating system can implement a name switch function
that decides what names should be resolved by which naming system.

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.

And with actively control I mean that any changes get planned and then designed.
And obviously this planning and designing should happen within the IETF when it
comes to new protocols.

I have created naming systems myself. And there are many reasons to dislike
DNS and do something different.

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.