[DNSOP] Strong objection to draft-wkumari-dnsop-alt-tld-04
Stephane Bortzmeyer <bortzmeyer@nic.fr> Sat, 14 February 2015 16:58 UTC
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43A701A6EED for <dnsop@ietfa.amsl.com>; Sat, 14 Feb 2015 08:58:11 -0800 (PST)
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
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 yQpa_Uw9mWd2 for <dnsop@ietfa.amsl.com>; Sat, 14 Feb 2015 08:58:08 -0800 (PST)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [217.70.190.232]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7505E1A6F11 for <dnsop@ietf.org>; Sat, 14 Feb 2015 08:58:08 -0800 (PST)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id B82683A654; Sat, 14 Feb 2015 17:58:06 +0100 (CET)
Received: by mail.sources.org (Postfix, from userid 1000) id 423BE190CAB; Sat, 14 Feb 2015 17:56:30 +0100 (CET)
Date: Sat, 14 Feb 2015 17:56:30 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Message-ID: <20150214165630.GB3616@sources.org>
References: <20150212063638.GD6950@mx1.yitter.info>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20150212063638.GD6950@mx1.yitter.info>
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux 7.7
X-Charlie: Je suis Charlie
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/qD0bvy2UVXno92h5IPLOBfdUs6o>
Cc: dnsop@ietf.org
Subject: [DNSOP] Strong objection to draft-wkumari-dnsop-alt-tld-04
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sat, 14 Feb 2015 16:58:11 -0000
On Thu, Feb 12, 2015 at 02:36:39PM +0800, Andrew Sullivan <ajs@anvilwalrusden.com> wrote a message of 20 lines which said: > Warren and I have prepared draft-wkumari-dnsop-alt-tld-04. We'd > appreciate feedback. If there isn't any, maybe that's a sign that > we could just publish it and thereby create a special TLD in which > people could set up their various special use special names? This is a bad idea and should be dropped completely. The main reason why I say so is that we already have RFC 6761 and it exists precisely to register special names. I was not a big fan of this RFC (that's an understatement) but, now that it exists, I see no reason to obsolete it after only two years of existence and only one TLD, an Apple's one, registered. Worse, draft-wkumari-dnsop-alt-tld-04 misrepresents RFC 6761 by saying things like "Special Use TLDs which should only be used in exceptional circumstances" while it is never written in RFC 6761. Other reasons: * existing code will not be modified and the names in draft-grothoff-iesg-special-use-p2p-names will have to be considered anyway. So, .ALT adds work for dnsop / the IESG without addressing the existing requests (.ONION, .GNU, .IP2P, etc). * the draft is confused in terminology between "domain name" and "DNS name". There is no such thing as a "DNS name". Domain names can be looked up in the DNS but they are used in many different contexts and can be resolved by several protocols. If someone sets up a RDAP server for Namecoin, names in .BIT or .COM will use the same protocol for information retrieval. * the draft uses terms like "pseudo-TLD" which are uselessy deprecative. * .ALT claims to be registered under the RFC 6761 framework but the draft ignores the requirments of its section 5.
- [DNSOP] draft-wkumari-dnsop-alt-tld-04 Andrew Sullivan
- Re: [DNSOP] draft-wkumari-dnsop-alt-tld-04 George Michaelson
- Re: [DNSOP] draft-wkumari-dnsop-alt-tld-04 Ted Lemon
- Re: [DNSOP] draft-wkumari-dnsop-alt-tld-04 George Michaelson
- Re: [DNSOP] draft-wkumari-dnsop-alt-tld-04 David Conrad
- Re: [DNSOP] draft-wkumari-dnsop-alt-tld-04 George Michaelson
- Re: [DNSOP] draft-wkumari-dnsop-alt-tld-04 Paul Vixie
- Re: [DNSOP] draft-wkumari-dnsop-alt-tld-04 David Cake
- Re: [DNSOP] draft-wkumari-dnsop-alt-tld-04 George Michaelson
- Re: [DNSOP] draft-wkumari-dnsop-alt-tld-04 Ed Pascoe
- Re: [DNSOP] draft-wkumari-dnsop-alt-tld-04 Edward Lewis
- [DNSOP] Strong objection to draft-wkumari-dnsop-a… Stephane Bortzmeyer
- Re: [DNSOP] Strong objection to draft-wkumari-dns… David Conrad
- Re: [DNSOP] Strong objection to draft-wkumari-dns… Warren Kumari
- Re: [DNSOP] Strong objection to draft-wkumari-dns… hellekin